ShareWare OnLine 2/ShareWare OnLine Volume 2 (CMS Software)(1993).iso/bbsdoors/valen110.zip/VALENCE.ORG

Text File | 1993-04-01 | 13KB | 257 lines

; :::: VALENCE.CFG ::::

; This is the main config file for Valence. You can edit it with any text
; editor - "2-Sysop", "TextEdit" from Searchlight works nicely.

; The format of this file is loosely inspired by Squish's COMPRESS.CFG, and
; I use most of the same code to read both files. It's based on "keywords".
; Some keywords use the rest of the line as a parameter; some work simply by
; being there. Case of keywords and leading and trailing spaces are ignored.
; The order of the keywords is not important; all lines in this file may be
; rearranged any way you see fit.

; There are default values for ALL keywords, so you can omit ANY of them.
; Valence will give you an error if it can't find this file, but it will in
; fact run if VALENCE.CFG is nothing more than a single blank line (try it
; and see!).

; This file may look a bit dauntingly long, but most of the length is in the
; comments. VALENCE.ORG is self-documenting. :-)

; All comment lines (like this one) beginning with a ";" and all blank lines
; are ignored and can be removed. And after you've read and understood this
; file, I recommend you remove them. Keep the original archived, though. :-)

; You can add comments to any line; anything after the ";" will be ignored.
; "Uncomment" means to remove the initial ";" from a line.

;---------Important Part for Quick Start----------------------------------

; All these fields should be changed to fit your BBS:

BBSID     NAKED                    ; BBS ID

; This is the filename that will be used for QWK packets downloaded from
; your BBS and REP packets uploaded to it. It should be 1-8 characters, and
; a legal DOS filename. I discourage the use of numerals in the name. If a
; user has numbered packets selected, the effective length of the name on
; QWK packets is limited to six characters, but you can still specify all
; eight, and all will be used for the REPs. Case is ignored.

; The BBSID should usually reflect the name of the BBS, and should be
; unique, or at least unique to your area. The BBSID here, "NAKED", is for
; "The Naked Singularity", my as-yet non-existent BBS. (And the name of my
; Demo Searchlight BBS, running on an 800k 3.5" disk.) I am hereby publicly
; staking claim to the name; DON'T ANYBODY STEAL IT! :-)

Sysop     William McBrine          ; Sysop's name

; This name is used both in CONTROL.DAT, and in the "To:" and "From:" fields
; of message headers in place of "SYSOP" if you have Sysop Renaming on (see
; below). Case is ignored. If you omit this keyword, and you're using
; Searchlight 3.0+, Valence will read the "sysopname" field in USER.SL2.

Locale    Salisbury, NC            ; City, State [, Country]
Phoneno   704-633-7817             ; BBS Phone #

; These two fields are optional and are only used in CONTROL.DAT. I've seen
; many systems that omit this info from their packets. If you want to, just
; delete these lines.

; Note the number here is actually my voice number; but I don't recommend
; you call, as you'll most likely get my father's answering machine. Leave a
; message for me and I'll call you collect. My father's name is the same as
; mine, so mention what you're calling about and/or ask for "Billy" (NOT
; "Bill"; he goes by that, too).

;---------You can ignore the rest if desired-----------------------------

; However, I recommend that you don't. :-)

;Welcome   LOGIN.ANS               ; \
;News                              ;  }- (ANSI)
;Goodbye   LOGOFF.ANS              ; /   Path defaults to SL's text dir

; These are optional ANSI files that may be included in the QWK packet.
; "Welcome" is usually displayed when a packet is opened, and "Goodbye" when
; you're done reading it. "News" is supposed to be important BBS news.
; There's no News feature in Searchlight, as there is in many other BBSes,
; so you can implement this any way you like, or not at all. By default
; (user-selectable), the News file is only included if it's been updated
; since the last time the user read it, as judged by file date. The other
; two files are always included, if they exist.

; By default, these files appear just as they would from within Searchlight,
; with full metacharacter and color code replacement. This is user-
; selectable. Unlike Searchlight, Valence has a 255-character-per-line
; limit on these files; the excess will be truncated. I expect to correct
; this in a future version - but the reader I use myself, SLMR 2.1a, won't
; read lines longer than 255 characters anyway (as I discovered when I used a
; different copying routine in an earlier version of Valence), and I
; imagine this applies to many other readers as well.

; You can add a News file within SL by using internal command #160 (I
; think), "Display file", in an autoexecuting menu in an appropriate place,
; like before the Bulletins. Making it pop up only when updated requires a
; little more...

; LOGIN.ANS and LOGOFF.ANS are the default values for Welcome and Goodbye;
; uncomment and edit these keywords only if you want to use different files,
; or none (make them blank for none). News defaults to none.

;Archiver  ZIP                     ; Default archiver name (NOT extension)

; This is the archiver assigned to new Valence users before they make their
; own selection (which many probably never will). "ZIP" is the default here.
; If you want a different default archiver or you don't have a "ZIP" entry
; in your COMPRESS.CFG, uncomment this and change it. (See my COMPRESS.CFG
; for more info.)

;Compress  C:\SQUISH\COMPRESS.CFG  ; Path to COMPRESS.CFG

; This specifies the full pathname to your COMPRESS.CFG. Uncomment this if
; you're already using one somewhere (see my included COMPRESS.CFG for more
; info). The name can be omitted, in which case the path must end in "\".

;LocQWK    C:\SLMR\                ; Path to local QWK files

; This is the directory where Valence puts your QWK packets when you
; "download" from a local login. The path must end in a "\". Note that if
; this is on the same drive as the work directory, Valence will simply
; "rename" the file into the new directory, rather than copying it and
; deleting the original.

; Above is a sample value; the default is to use the directory the .EXE is
; in. Uncomment this if you want to change it.

;LocREP                            ; Path to local REP files

; Uncomment this and fill it in only if you want to use different
; directories for QWK and REP files; otherwise, the LocQWK path is used.
; Note this is also the path used for local PTR files.

; When "uploading" locally, your REP packets MUST be named "<BBSID>.REP",
; you MUST rename your pointer files to "<BBSID>.PTR", and you can only
; upload one at a time. Remote users can upload multiple packets or pointer
; files at once and can use names of the form "*.REP" and "<BBSID>.PT*" if
; using a batch protocol.

;WorkDir                           ; Path to work directory

; If you have a LARGE RAM disk, preferably one with over a meg free, you can
; speed Valence up a little by setting the work directory to the RAM disk.
; By default, Valence uses the directory the .EXE is located in as its work
; directory. (The actual "work directories" branch off this directory, and
; are named for the node that creates them - "1", "2", etc. These are
; deleted when the program terminates, unless it crashes badly.)

Rename                             ; Change SYSOP name

; This changes your name in the "To:" and "From:" fields of messages from
; "SYSOP" to whatever you put after the keyword "Sysop" (above). This can
; sometimes produce messages labelled as being from you when they're really
; from some other sysop on another board who didn't configure SLMAIL
; correctly, so you may want to comment it out. :-)

;ThreadOff                         ; Do not attempt threading

; By default, Valence will post uploaded replies with the "reference
; number" intact; that is, it will put the message number of the original in
; the "replyto" field of the new message. This allows the "Thread" command
; to work, and improves offline threading as well. But since QWK packets use
; the sequential message numbers, which get changed when a subboard is
; renumbered, the reference numbers will be all wrong if you frequently
; renumber your subboards. If you do, uncomment this keyword...

; ...or better yet, STOP doing it. I know there's another QWK door which
; INSISTS that you renumber, because it can't handle message numbers over
; 999. Mine, however, will handle numbers up to ten million minus one (the
; limit of the QWK format).

; Since the subboards most likely to get renumbered are echomail areas, and
; since inclusion of the reference number in downloaded QWKs is OFF by
; default for echomail areas (and ON for local areas), this may not be
; terribly important.

;RepKill                           ; Delete local .REPs on "upload"

; If you uncomment this keyword, your local .REP files will be deleted
; automatically after they're processed. This saves you from having to
; remember if you've uploaded them or not. The default is to leave them
; alone.

;MaxSub    65000                   ; Maximum possible messages per subboard
;MaxTotal  65000                   ; Maximum possible messages per packet

; In Valence, users have the option to set limits on the number of messages
; the program will collect into one packet, and the number of messages it
; will collect from each subboard at one time. These two keywords specify
; the MAXIMUM values they can set these options to. 65000 is the default and
; maximum for each value; 10 is the minimum. (It will be pulled into that
; range if you try to go outside. 0 and non-numeric values are converted to
; 65000.) Uncomment and change these only if you want different values.

; Note that regardless of the number of messages packed, users will not be
; able to download packets that would take them past their time limits, so I
; recommend leaving these limits alone. (65000 is essentially a non-limit.)
; Trying to download oversized packets is its own punishment. If they get
; too big, you can't even load them into a reader. However, if you do find
; you have a "message leech" problem, these keywords are here.

;DefSub     50                     ; Default maximum messages per subboard
;DefTotal  200                     ; Default maximum messages per packet

; These are the default values assigned to new users for maximum number of
; messages per subboard and packet. 50 and 200 are the rather arbitrary
; default defaults, :-) based only on the number Tom Curtis set for 2400 bps
; on The Big Byte BBS, in an older QWK door... I thought about applying some
; formula to these values to adjust them by bps rate, but decided against
; it. (I may do it in a later version if there's a strong demand.) Users are
; free to reset these values as they like, from 10 up to the limits
; specified in MaxSub and MaxTotal.

; The limits on message numbers are not checked when scanning the MAIL
; subboard, because it would be silly to leave out new private mail. This
; means that if you have someone who saves all their old mail online and has
; accumulated, say, 200 messages (don't laugh, I know a guy who did!), and
; they set Valence to include old mail, they could overrun the packet
; limit. However, no other subboards would then be scanned.

;LogFile   VALENCE%o.LOG               ; Path to Valence's Log file

; This is the text file where Valence keeps a record of who did what, for
; your perusal. No other use is made of this file, so you can turn it off if
; you like. The name above is the default, so uncomment this and edit it
; only if you want to change it. If the directory is not specified, the log
; file is created in the Valence directory. If you uncomment this keyword
; and make it blank, logging will be turned off.

; Note the use of Searchlight's "%o" metacharacter to specify the node
; number. This filename would translate to "VALENCE1.LOG", "VALENCE2.LOG",
; etc., as appropriate. Thus, you'll have seperate log files for each node.
; You can combine them into one by taking out the "%o", but I don't
; recommend this, as Valence may crash if two or more nodes run at the same
; time with the same log file.

; The %o can be used anywhere in the name, as can all the other Searchlight
; %-codes, plus the special code "%e" I invented to represent the directory
; of the current node's CONFIG.SL2. (See INTPROT.CFG for more info.) Thus
; you could have

; LogFile   %e\VALENCE.LOG

; to create the log file for each node in the node's home directory. Note
; also that the log file need not be exclusive to Valence, except while
; it's running; for an interesting effect, try:

; LogFile   %e\ACTIVITY.LOG

; This feature is NOT available for any of the other keywords in
; VALENCE.CFG.

; *** How to crash this program ***

; I've tried to make this program fairly crash-proof, but there are a few
; loopholes not worth coding around. Try putting wildcards in any of the
; fields here that call for a filename.